User-Centred Requirements Handbook |
The aim of this section is:
• To record information about similar, possibly competing, systems that may be included in the design of the new system. This will normally be attractive features that should be considered for inclusion. However problems with other systems that should be avoided in the new system may also be considered.
Process
Complete Table 1.9 below as follows:
1. List each of the user goals in column 1.
2. For each user goal, consider the functions of features to be included or excluded from the current system.
3. Write the name of the system that the function or feature relates to in column 2.
4. If the function or feature is to be included, write this in column 3. If it is to be excluded, write this in column 4.
Form 1.9 - Functions and features of similar systems (Example)
| 1.9 Functions and features of similar systems | ||||
| System: New bank machine | ||||
| Product name | Good feature to Include | Poor feature to Exclude | Ref. | |
| General ideas | ||||
| Goal Specific | ||||
|
G1 Access required service quickly and safely |
IBM Cash point Sirocco Corp. |
Non reflective screen |
Small buttons |
1.9.1 1.9.2 |
|
G2
|
AT&T Bank machine | Low warning before machine empty | 1.9.3 | |
|
G3 Replenish paper |
AT&T Bank machine | Low warning before machine empty | 1.9.4 | |
|
G4 Report fault with bank machine |
||||
|
G5 Repair fault |
Sperry Univac | Step-by-step diagnostic routine | 1.9.5 | |
Transfer to Form 3.5 Functions and Features
and to Form 3.4 Technical environment